Distributed client services based on execution of service attributes and data attributes by multiple nodes in resource groups

ABSTRACT

A network provides distributed client services based on participation in respective resource groups by computing nodes, each resource group including a corresponding resource requirement for any computing node that joins the corresponding resource group for execution of the corresponding distributed client service. Each computing node, in response to determining its corresponding available node capacity, is configured for selectively creating and joining at least one new resource group for execution of a corresponding distributed client service having a corresponding resource requirement, and/or selectively joining at least one of the available resource groups, based on the corresponding available node capacity satisfying the corresponding resource requirement. Each distributed client service also includes service attributes that define parameters for execution of the distributed client service, and data attributes that define the attributes required for data to be used in the distributed client service.

This application is a continuation-in-part of commonly-assigned,copending application Ser. No. 11/053,954, filed Feb. 10, 2005, entitled“DISTRIBUTED COMPUTING BASED ON MULTIPLE NODES WITH DETERMINED CAPACITYSELECTIVELY JOINING RESOURCE GROUPS HAVING RESOURCE REQUIREMENTS”, thedisclosure of which is incorporated in its entirety herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to distributed computing in a networkhaving multiple computing nodes. More particularly, the presentinvention relates to providing service virtualization of client-servertype computing services using a peer-to-peer architecture that relies onmultiple computing nodes for sharing tasks associated with providing theclient-server type computing services in a distributed environment.

2. Description of the Related Art

Distributed computing has evolved to technologies that enable multipledevices to share in providing a given service. One well-known exampleinvolves BitTorrent, where a single source file within a group ofBitTorrent users, called a swarm, spreads portions of a large data file(e.g., a digital movie, etc.) such that all members of the swarm have aportion of the large data file (a “chunk”) to share. After the initialdownloading of the portions to user computers, the portions of the datafile are then uploaded to other users in the swarm that need the chunks.The BitTorrent rules require every user of the swarm that performsdownloading to also do perform uploading. Hence, as more users attemptto download, the uploading capacity increases. Once all members of theswarm have shared all their chunks, all the members have their owncomplete source.

Hence, Bit-Torrent presumes that multiple copies of data are present ona peer-to-peer network; hence, it is presumed that the data will persistbeyond the existence of the source that added the data to the network.Further, Bit-Torrent assumes that clients are unreliable and maydisappear from the network, for example if a client device logs off thenetwork. Consequently, Bit-Torrent relies on multiple copies of data onthe network, where peers replicate the data to provide a largerdistribution of the data.

Although BitTorrent has been demonstrated to be highly effective inapplications such as file sharing, BitTorrent is modeled as apeer-to-peer application. Unlike client-server based applications suchas web hosting, e-mail, etc., peer-to-peer applications are designedsuch that a peer client is configured for communicating with adestination peer client, and is not configured for obtaining anyknowledge relating to network topology; hence, a peer client may beunaware that it is communicating with a cluster of servers. In addition,all peer devices must be online in order for any peer-to-peer services(e.g., instant messaging) to be operable. Hence, unlike client-servercomputing that relies on servers to provide persistent application stateto enable management client transactions generated from client devicesthat have a limited network presence, there is no persistent state ofclient transactions in the network in peer-to-peer computing.

Hence, a fundamental problem between peer-to-peer computing andclient-server computing involves reconciling the mutually incompatiblefeatures in a manner that would permit applying the advantages ofpeer-to-peer networking to client/server-based applications.

One technique utilized by UNIX programmers involves implementing serversoftware on the same machine as a device executing client applications,referred to herein as a client device or user node. Unfortunately,attempts to implement servers on client devices are not practical,because the design of server protocols are inherently scarce resourceprotocols, and are not designed to scale with an exponential increase inthe number of clients. For example, servers (e.g., Microsoft ExchangeServers) typically require persistent connections (e.g., TCPconnections) between each other in order to synchronize data, where eachadditional server requires added connections between the new server andthe existing servers, plus return connections, where the number ofconnections (N) between servers (S) is N=S*(S−1). Hence, a linear growthin the number of servers results in an exponential growth in the numberof connections between the servers. Consequently, many enterprise-classapplications utilize server-based protocols that require synchronizationamong multiple servers.

As described above, peer-to-peer applications are not configured forobtaining any knowledge relating to network topology, and cannot providea persistent state of client transactions. Hence, client-server-basedapplications cannot readily be modified for deployment execution on apeer-to-peer type architecture. Further, if the client device is notpresent (i.e., logged onto the application service) the participation ofthat client device in the application service is nonexistent. Inaddition, existing messaging servers (e.g., AOL instant messenger) areutilized solely to provide directory services in identifying users, anddo not participate in providing services related to the actualapplication (e.g., data transfer) between client devices.

Hence, a fundamental problem in the conventional technologies is thatenterprise-level applications, and consumer-level applications aredesigned according to a client-server architecture model. As describedabove, the client-server architecture model inherently cannot beimplemented in a scalable manner as distributed servers manner due tothe exponential nature of synchronization.

SUMMARY OF THE INVENTION

There is a need for an arrangement that enables client-server basedapplications (e.g., e-mail applications, web server applications, etc.),to be implemented in a scalable manner according to a distributedcomputing architecture that enables replication of data and servicesbetween client devices, eliminating the necessity of centralizedservers.

There also is a need for an arrangement that enables existingapplications that are designed according to a client-server architecturemodel to be deployed in a distributed network that enables peer-to-peerfunctionality and client-server functionality to exist in the samenetwork in a scalable manner. In particular, there is a need for anarrangement that enables applications to be implemented using thescalable attributes of peer-to-peer networks, while also utilizing theclient-server attributes that are optimum for enterprise-scale networkapplications.

There also is a need for an arrangement that enables an infrastructureto support a traditional client-server service, such that the serverapplication that typically has provided the service can be distributedamong one or more computers utilizing a peer-to-peer level protocol, theserver application also being able to be executed on the same devicetypically used for executing the client application.

There also is a need for an arrangement that enables each of thecomputing nodes in a distributed network to adaptively participate in asmany distributed services as desirable, based on the capacity of thecorresponding computing node, enabling user nodes to participate inproviding distributed services.

These and other needs are attained by the present invention, where anetwork provides distributed client services based on participation inrespective resource groups by computing nodes, each resource groupincluding a corresponding resource requirement for any computing nodethat joins the corresponding resource group for execution of thecorresponding distributed client service. Each computing node, inresponse to determining its corresponding available node capacity, isconfigured for selectively creating and joining at least one newresource group for execution of a corresponding distributed clientservice having a corresponding resource requirement, and/or selectivelyjoining at least one of the available resource groups, based on thecorresponding available node capacity satisfying the correspondingresource requirement. Each distributed client service also includesservice attributes that define parameters for execution of thedistributed client service, and data attributes that define theattributes required for data to be used in the distributed clientservice. Hence, distributed client services can provided by multiplecomputing nodes, including user nodes, enabling client services to beprovided using a distributed peer-to-peer architecture.

One aspect of the present invention provides a method in a computingnode. The method includes determining an available node capacity for thecomputing node relative to any resource groups having been joined by thecomputing node, each resource group having a corresponding resourcegroup attribute specifying a resource requirement for providing acorresponding distributed client service within a network, a serviceattribute that defines parameters for execution of the correspondingdistributed client service, and a data attribute that defines servicedata to be used in providing the corresponding distributed clientservice for a client. The method also includes selectively joining atleast one of the resource groups based on the corresponding resourcerequirement being less than the available node capacity. The method alsoincludes executing the distributed client service for the correspondingat least one resource group having been joined by the computing node,according to the corresponding resource group attribute, includingreplicating the corresponding service data among any other computingnodes belonging to the at least one resource group according to thecorresponding service attribute and the corresponding data attribute.The selective joining of a resource group enables each computing node todecide whether it prefers to join as many resource groups as desired,based on the available node capacity. In addition, the service attributeensures that execution of the distributed client service is consistentamong all computing nodes belonging to the resource group, while thedata attribute ensures that the appropriate service data is replicatedamong the computing nodes of the resource group, enabling clients toaccess the identical client service and data from any one of thecomputing nodes, including where the client resides on one of thecomputing nodes.

Another aspect of the present invention provides a method in a network.The method includes providing resource groups, each resource grouphaving a corresponding resource group attribute specifying a resourcerequirement for providing a corresponding distributed client servicewithin the network, a service attribute that defines parameters forexecution of the corresponding distributed client service, and a dataattribute that defines service data to be used in providing thecorresponding distributed client service for a client. Each computingnode of the network (1) determines a corresponding available nodecapacity relative to any of said resource groups having been joined bythe computing node, (2) selectively joins at least one of the resourcegroups based on the corresponding resource requirement being less thanthe available node capacity, and (3) executes the distributed clientservice for the corresponding at least one resource group having beenjoined by the computing node, according to the corresponding resourcegroup attribute. The method also includes connecting a client, of thedistributed client service, to the distributed client service via one ofthe computing nodes having joined the corresponding resource group.Further, each of the computing nodes having joined said at least oneresource group perform the executing of the distributed client servicebased on replicating the corresponding service data among each of theother computing nodes belonging to the corresponding at least oneresource group, according to the corresponding service attribute and thecorresponding data attribute.

Additional advantages and novel features of the invention will be setforth in part in the description which follows and in part will becomeapparent to those skilled in the art upon examination of the followingor may be learned by practice of the invention. The advantages of thepresent invention may be realized and attained by means ofinstrumentalities and combinations particularly pointed out in theappended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference is made to the attached drawings, wherein elements having thesame reference numeral designations represent like elements throughoutand wherein:

FIG. 1 is a diagram illustrating a distributed network having multiplecomputing nodes configured for providing distributed client servicesbased on having joined multiple resource groups, according to anembodiment of the present invention.

FIGS. 2A and 2B are diagrams illustrating resource group attributes andnode attributes that specify reserved resources and available nodecapacity, respectively.

FIG. 3 is a diagram illustrating one of the computing nodes, accordingto an embodiment of the present invention.

FIG. 4 is a diagram illustrating distributed computing services providedby computing nodes of a resource group, including by one of thecomputing nodes following a disconnect from the resource group.

FIG. 5 is a diagram illustrating the method of joining resource groupsfor execution of distributed client services by computing nodes,according to an embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

The disclosed embodiment is directed to multiple computing nodes thatare configured for joining a resource group in order to providedistributed client services. The ability to provide distributed clientservices is implemented based on numerous advantageous features,described in detail below, that address various aspects of distributedcomputing such as data replication, arbitration of data access andcontrol, organizing computing nodes to provide distributed clientservices, identification of the computing nodes providing the desireddistributed client services, plus identification and management of thereplicated data objects into a distributed file system. These featureswill be described below, followed by a description of utilizing thesefeatures in order to provide distributed client services in a network.First, however, a brief overview of distributed services according tothe disclosed embodiment will be provided.

Overview of Distributed Client Services

The disclosed embodiment is directed to implementing client-server basedapplications that are implemented using a peer-to-peer based topology,enabling the client-server based applications to be implemented in anetwork as distributed client services. Hence, service data associatedwith a given client service is distributed throughout the network,ensuring security and data integrity in case one or more network nodesare unavailable. Moreover, use of a peer-to-peer based topology enablesmultiple computing nodes to provide the same client service, enablingany client to access any one of the computing nodes for the desiredclient service.

More fundamentally, the disclosed embodiment enables client services tobe implemented in a manner that eliminates the necessity of serverscommunicating via inter-server connections that have severely restrictedthe scalability of conventional servers.

For example, in a traditional (prior art) SMTP environment,client-server protocols assume that an e-mail client is executing on aclient device, and that an e-mail server is executing on a serverdevice. Hence, if an e-mail client is disconnected from the serverdevice, the e-mail client is unable to receive messages from the e-mailserver (e.g., according to POP3 or IMAP protocols), and the e-mailclient is unable to send messages to the e-mail server (e.g., accordingto SMTP protocol). At most, the e-mail client only can transfer outgoingmessages to a send cache (e.g., an outbox) within the client device forawaiting transfer upon reconnection with the e-mail server via an SMTPconnection. The source e-mail server (e.g., Server 1) then stores thee-mail messages sent from the originating client (Client 1). The sourcee-mail server (Server 1) periodically collects all e-mail messages thatneed to be sent to a destination server (e.g., Server 2), establishes aconnection with the destination server using a prescribed mail transferprotocol (similar to SMTP), and transfers the e-mail messages from thesource e-mail server (Server 1) to the destination server (Server 2).The destination server (Server 2) then parses the received e-mailmessages, and stores the received e-mail messages and appropriatedestination folders for destination e-mail clients. Each destinationuser (e.g., Client 2) then logs into the network, establishes aconnection with the destination server (Server 2), for example accordingto POP3 or IMAP protocols, in order to retrieve the e-mails from theappropriate destination folder. Once the destination server (Server 2)authenticates the destination user (e.g., Client 2), the destinationserver supplies the e-mails from the destination folder to the clientdevice.

Hence, e-mail communications in conventional client-server e-mailsystems inherently will suffer a delay in service if there is a loss ofconnectivity between any one of three connections, namely the sourceclient to the source server connection, the source server to destinationserver connection, or the destination server to destination clientconnection.

As described in detail below, the disclosed embodiment enables theelimination of conventional client-server models by enabling anycomputing node, including user nodes implemented as laptop computers, todecide whether to participate in providing the distributed clientservices. Distributed client services may include replication of dataamong the computing nodes participating in the distributed clientservices, referred to herein as a resource group, where data ownership(i.e, authority to decide read/write access) is passed between thecomputing nodes using locality control objects, also referred to ascontrol tokens.

In addition, a given computing node can continue providing thedistributed client services, even if the computing node is disconnectedfrom the network, for example in the case of a user traveling with hisor her laptop; in this case, a client resource on the user laptop isstill able to obtain network-based distributed client services, eventhough the user laptop is disconnected from the network. Further, thedecision whether to participate in providing a distributed clientservice, based on joining a resource group, rests solely on thecomputing node, limiting concerns that a computing node may beoverwhelmed with processing requests.

The following description will describe in further detail thedistributed network architecture that enables individual computing nodesto decide whether to participate in providing a distributed clientservice, followed by a description of execution of a distributed clientservice.

Overview of Distributed Network and Selective Joining of Resource Groups

FIG. 1 is a diagram illustrating a network 10 having a directory service12 and a plurality of computing nodes 14 configured for providingdistributed computing services (e.g., distributed client services) basedon having joined resource groups 16, according to an embodiment of thepresent invention. In particular, each distributed computing serviceprovided by the network 10 is implemented based on deployment ofmultiple resource groups 16 (e.g., S1, S2, S3, and S4), wherein eachresource group 16 has its own corresponding set of resource groupattributes 22. For example, the resource group “S1” 16 may beestablished for providing distributed client services related toe-commerce, for example customer e-mail services, web hosting, onlinetransaction management, order processing, and billing operations, etc.,where each service is executed based on distributed processing by eachof the connected computing nodes 14; the resource group “S2” 16 may beestablished for providing enterprise based services, for exampleemployee file systems (data storage and retrieval), directory servicesincluding the directory service 12, or telephone directory services,accounting management, etc.; similar distributed services may beprovided by the other resource groups “S3” and “S4”. As described belowwith respect to FIG. 2A, the resource group attributes 22 for eachresource group define both the resource requirements 20 necessary forany computing node to join the resource group, and the attributes 24 ofthe data replicated and/or executable resources that executed by each ofthe joined computing nodes 14 in order to provide the distributedservices to client nodes 18.

The directory service 12, implemented for example as one of thedistributed services provided by one of the resource groups 16, isconfigured for providing resolutions for identifying available resourcegroups 16 for clients 18 (i.e., client-based executable applicationresources that are executing on a given user device) attempting toobtain a corresponding distributed service, and computing nodes 14attempting to join a resource group to provide distributed processing.The query issued may specify different attributes about the service, forexample service type (e.g., e-mail, e-commerce, accounting, databasemanagement), data type (e.g., e-mail data for user names starting withA-L and not L-Z), or some other class identification (e.g., corporate,engineering, marketing, legal, etc.).

Additional details related to the directory service 12 can be obtainedfrom commonly-assigned, copending application Ser. No. 11/000,041, filedDec. 1, 2004, entitled “ARRANGEMENT IN A SERVER FOR PROVIDING DYNAMICDOMAIN NAME SYSTEM SERVICES FOR EACH RECEIVED REQUEST”, the disclosureof which is incorporated in its entirety herein by reference. Insummary, a Domain Name System (DNS) server 12 is configured fordynamically selecting, for a client 18 or a computing node 14 requestinginformation, a selected resolution from available resolutions, theselected resolution identifying at least one destination for thespecified service. The dynamic selection of the selected resolution isbased on an attribute of the requesting entity (e.g., client 18 orcomputing node 14) and/or a determined attribute of the network. Hence,the selected resolution directs the requesting entity to a specificdestination (e.g., a specific computing node 14 of a given resourcegroup 16) based on prescribed selection criteria, for example servicelevel agreements, the location of the client device, network performanceor detected congestion conditions, authentication of the user of theclient device, etc. The selected resolution also can be for enforcementof load balancing policies.

Each computing node 14 is configured for selectively joining anavailable resource group 14, or creating a new resource group 14, basedon determining whether the available node capacity for the computingnode 14 is sufficient for the resource requirement 20 specified for thecorresponding resource group 14. Once a computing node has joined aresource group 16, the joining of the resource 16 is registered with thedirectory service 12, and clients 18 can be connected to a computingnode 14 that provides the corresponding distributed service, based onthe directory service 12 responding to a query identifying one of thedistributed client services by redirecting the client node 18 to one ofthe computing nodes 14 that joined the appropriate resource group 16.

Since a computing node 14 is configured for selectively joining aresource group 16 based on the computing node 14 deciding whether it hassufficient available node capacity for the corresponding resourcerequirement 20, smaller computing nodes 14 (e.g., N1, N2, N5, N6) thathave only a limited amount of resources, for example only 160 gigabytes(GB) of storage capacity (or, for example, a limited CPU processingcapacity), are able to provide a contribution to available resourcegroups 16 based on their relative available node capacities. Forexample, computing nodes N1 and N2 belong only to resource groups S1 andS2, computing node N5 belongs only to resource groups S3 and S4, andcomputing node N6 belongs only to resource groups S1 and S4.

Computing nodes 14 having substantially larger available nodecapacities, for example at least an order of magnitude greater (i.e., adifference of at least 10 times) (e.g., N4 having 1600 GB (1.6 TB)storage capacity, N3 having 2.5 Terabyte (TB) storage capacity) also canjoin the same resource groups 16 as the smaller computing nodes, sinceeach computing node (e.g., N1, N2, N3, N4, N6) having joined a givenresource group (e.g., S1) is required to provide only the amount ofresources specified by the corresponding resource requirement 20 (R1).Hence, different sized computing nodes 14 can join the same resourcegroup 16, even if the computing nodes 14 differ in size by orders ofmagnitude.

In addition, since each computing node 14 selectively joins a resourcegroup 16 based on whether the corresponding resource requirement 20 isless than the available node capacity, larger nodes (e.g., N3) can joina greater number of resource groups 16, enabling the larger computingnode 14 to provide virtualized services to a substantially larger numberof resource groups. As illustrated in FIG. 1, the larger computing node“N4” is able to join the resource groups S1, S3, and S4, and the largestillustrated computing node “N3” is able to join all of the illustratedresource groups S1, S2, S3, and S4 due to its substantially largecapacity. Consequently, the network 10 may be composed of smallercomputing nodes N1, N2, N5, N6 14 (e.g., laptop computers) that may onlyhave sufficient capacity to join one or two resource groups 16, whereaslarger computing nodes N3, N4 14 (e.g., fixed data centers) may be ableto join hundreds or even thousands of resource groups 16, as needed.

FIG. 2A is a diagram illustrating resource group attributes 22 for agiven resource group 16, including the associated resource requirement20 necessary for a computing node 14 to join the resource group 16,according to an embodiment of the present invention. The resource groupattributes 22 for a given resource group 16 include the resourcerequirements 20 that need to be reserved by each computing node 14 thatjoins the resource group 16, and distributed computing serviceattributes 24 that describe in detail the distributed computing serviceprovided by each of the computing nodes 14 having joined the resourcegroup 16. For example, the resource group “S1” may have computingservice attributes 24 that specify service attributes 26 related to thetype of distributed service being provided (e.g., e-mail application,directory services applications such as directory service 12, e-commerceapplications, data processing or database applications, financialtransaction applications, etc.). The computing service attributes 24also may specify data attributes 28 that specify the attributes of thedata that is replicated among the computing nodes 14 belonging to theresource group 16. For example, the data attributes 28 may specifyfeatures such as data type (e.g., e-mail message, word processingdocument, spreadsheet, database object, etc.) source of the data (e.g.,author, e-mail composer, financial transaction identifier, etc.) timeand date of creation, security key identifiers, or any other classattribute that may be used to classify the data.

Hence, each resource group 16 can be defined based on the attributes 26of the services being provided, as well as the attributes 28 of the datawhich is replicated among the computing nodes 14. Also apparent from theforegoing is that each of the computing nodes 14 that belong to a givenresource group 16 can respond to a given service attribute 26 thatspecifies that all data is to be replicated among the computing nodes ofthe resource group 16, and that each computing node 14 of the resourcegroup 16 has authority to modify the data or create new data, and arequirement to update the other computing nodes 14 of any modificationor creation to ensure data is synchronized.

An exemplary method of replicating data among the computing nodes 14 isdisclosed in commonly-assigned, copending application Ser. No.10/859,209, filed Jun. 3, 2004, entitled “ARRANGEMENT IN A NETWORK NODEFOR SECURE STORAGE AND RETRIEVAL OF ENCODED DATA DISTRIBUTED AMONGMULTIPLE NETWORK NODES”, the disclosure of which is incorporated in itsentirety herein by reference. In summary, data is stored using amongcomputing nodes 14 based on encoding of the data into multiple distinctencoded data units according to a prescribed encoding operation (e.g.,Reed Solomon-based N of M encoding). The secure encoding operationgenerates a first prescribed number (e.g., M=7) of encoded data units,whereas merely a second prescribed number (e.g., N=4) of the encodeddata units are necessary for recovery of the original data, the secondprescribed number being less than the first prescribed number. Theencoded data units are distributed among the computing nodes 14 of theresource group 16, where any one network node can receive less than thesecond prescribed number if security is needed. A requesting node 14recovers the original data by requesting the second prescribed number ofencoded data units from among the computing nodes 14 having stored therespective encoded data units.

In addition, only the computing nodes 14 that belong to the resourcegroup 16 have authority to modify the associated data, such thatnon-members cannot modify the data of the resource group. Ownership ofauthority to modify data is described in commonly-assigned, copendingapplication Ser. No. 10/859,208, filed Jun. 3, 2004, entitled“ARRANGEMENT IN A NETWORK FOR PASSING CONTROL OF DISTRIBUTED DATABETWEEN NETWORK NODES FOR OPTIMIZED CLIENT ACCESS BASED ON LOCALITY”,the disclosure of which is incorporated in its entirety herein byreference.

FIG. 2B is a diagram illustrating a resource table 30 maintained by eachcomputing node 14 in order to track reserved (i.e., allocated)resources, and available node capacity, according to an embodiment ofthe present invention. In particular, each computing node 14 determinesfor itself the available node capacity 32, which may be measured forexample in terms of storage capacity 34, device bandwidth 36,transaction capacity 38, CPU load 40, etc. The resource table 30 alsoincludes reserve entries 34 that specify the amount of resources thatare reserved for respective resource groups to which the computing nodeis a member (e.g., S1, S2), plus resources reserved for system use bythe computing node 14, described below.

Hence, each computing node 14 is able to determine whether it wants tojoin any given resource group 16 based on comparing the resource groupattributes 24 with internal computing node attributes (not shown) thatspecify preferences for the types of distributed services the computingnode 14 should provide. For example, a computing node 14 may includeinternal computing node preferences (not shown) to indicate thecomputing node 14 should avoid database management services or financialtransaction services, but should join any distributed servicesassociated with a prescribed class of service, for example e-mail serverapplications, Web hosting applications, Voice over IP applications, etc.In addition, the computing node 14, upon determining that it wishes tojoin a given resource group, can compare the resource requirement 20 ofthat resource group 16 with the available node capacity 32 in order todetermine whether the computing node 14 has sufficient availableresources to join that resource group 16.

FIG. 3 is a diagram illustrating in detail one of the computing nodes 14of FIG. 1, according to an embodiment of the present invention. Eachcomputing node 14 includes computing node resources 42 including aprocessor unit 44, processor memory 46, data storage 48, and a networkinterface 50. As illustrated in FIG. 3, the data storage 48 includes areserved portion 52 for storage of system data, reserved portions 54 aand 54 b for storage of data associated with respective joined resourcegroups “S1” and “S2”, and an available storage portion 56 that is freespace that is available for use. As illustrated in FIG. 3, the executionof software by the processor 44 using processor memory 46 may result ininstantiation and execution of executable processes 58 a and 58 b forthe respective resource groups “S1” and “S2”, where each of theprocesses 58 a and 58 b may include their own distinct operatingsystems, applications, etc.

As illustrated in FIG. 3, the CPU 44, the processor memory 46, and anetwork interface 50 each have portions of their respective resourcesallocated for system use, the joined resource groups “S1” and “S2” andavailable capacity that is available for use.

The computing node 14 also includes a resource monitor 62 configured forcontinually monitoring the resource utilization in each of the computingnode resources 44, 46, 48, and 50, and updating the resource table 30 toindicate the amount of computing node resources that are consumed byeach of the joined resource groups 16 relative to the reserved capacityas specified in the resource table 30. The resource monitor 62 also isconfigured for determining the available node capacity 32 based oncomparing the total system capacity minus the reserved capacity 34 thathas already been allocated.

The computing node 14 also includes a resource group arbitration module60 configured for reading the resource table 30 in order to identify theavailable node capacity 32 determined by the resource monitor 62. Theresource group arbitration module 60 is configured for selectivelycreating a new resource group 16, as needed for example due to internalattributes including administrator settings, etc. The resource grouparbitration module 60 also is configured for identifying availableresource groups 16, for example by accessing the directory service 12,and selectively joining resource groups 16 based on the associated groupattributes 24, and also based on whether the resource requirement 20 ofthe available resource group 16 is less than the available node capacity32. Based on the available node capacity 32 being sufficient for theresource requirement 20, the arbitration module 60 can allocated reservecapacity 34 and join the resource group 16, if desired. If after joiningthe resource group 16 and allocating the corresponding reserve capacity34 the arbitration module 60 identifies that available node capacity isstill present, the arbitration module 60 can continue to selectivelyjoin additional resource groups 16 based on the available node capacity32 being sufficient for the corresponding resource requirement 20.

As illustrated in FIG. 3, the computing node 14, if implemented as auser device (e.g., a laptop computer), also may include executableclient application resources, for example an e-mail client 61 and aword-processing client 63. The e-mail client is configured for accessinga prescribed e-mail service: the operating system underlying the e-mailclient 61 establishes a connection 65 with the appropriate e-mailservice, in this case the application processes 58 a providing thedistributed e-mail service within the resource group “S1” 16.

Similarly, the operating system underlying the word processing client 63establishes a connection 67 with the appropriate file service, in thiscase the application processes 58 b providing the distributed fileservice within the resource group “S2” 16. Additional details related toproviding a distributed file service is described in commonly-assigned,copending application Ser. No. 11/051,333, filed Feb. 7, 2005, entitled“ARRANGEMENT FOR A DISTRIBUTED FILE SYSTEM HAVING DATA OBJECTS MAPPEDINDEPENDENT OF ANY DATA OBJECT ATTRIBUTE”, the disclosure of which isincorporated in its entirety herein by reference. In summary, each datafile of a distributed file system is identified by a correspondingglobally-unique object identifier that is independent of any attributeof the data file. The distributed file system is established for eachresource group 16, such that each resource group 16 has its owndistributed file system. A node 14 in the distributed file system (i.e.,a node belonging to the corresponding resource group 16) has a filesystem that includes a plurality of directory entries, where eachdirectory entry has a file name field, an attributes field, and anobject identifier field configured for specifying a globally-uniqueobject identifier. The globally-unique object identifier is universallyreachable by any computing node 14 of the distributed file system forthat resource group 16 and uniquely identifies the data file, enablingthe data file to be universally identifiable by any node 14 in theresource group 16 based on the corresponding object identifier. The datafile can be stored independently of a device file system based onproviding a resolution between the data file name and its objectidentifier, followed by a resolution between the object identifier and aselected location for the data file.

Distributed Client Services

FIG. 4 is a diagram illustrating distributed computing services providedby computing nodes of a resource group, including by one of thecomputing nodes following a disconnect from the resource group. Asillustrated in FIG. 4, the computing nodes N1 and N2 provide thedistributed client service 76, for example a distributed e-mail service,based on concurrent execution of the required application processes 58 ain accordance with the service attributes 26 of the resource group 16,and storage and replication of the service data 54 a in accordance withthe data attributes 28. In other words, each computing node 14independently executes its corresponding application process 58 a inaccordance with the service attributes 26, including manipulating thelocally-stored service dated 54 a accordingly. If the applicationprocess 58 a detects that the another computing node is reachable, thenthe application processes 58 a interact for synchronization of theservice data 54 a, and any necessary arbitration, for exampleidentifying which computing node should possess the locality controlobject 70 for a given data object 72.

As illustrated in FIG. 4, the distributed client service 76 executed bythe executable process 58 a in the computing node N1 is configured forreceiving an e-mail message “E-mail Msg1” 72 from the e-mail client 18 aat event 64. The application process 58 a determines from the dataattributes 28 that the message 72 has the appropriate attributes, andreplicates the e-mail message “E-mail Msg1” 72 to all reachablecomputing nodes at event 66. The application process 58 a in thecomputing node N1 also creates for the e-mail message “E-mail Msg1” 72 alocality control object (LCO_(Msg1)) 70, and selectively passes thelocality control object (LCO_(Msg1)) at event 66 to the computing nodemost appropriate to retain ownership of the corresponding e-mailmessage, namely the computing node “N2” 14 that is most likely toprovide distributed e-mail services for the destination client (e.g.,Client 2) 18 b.

Assuming the e-mail client 18 b had transmitted an e-mail message“E-mail Msg2” 72 at event 63 prior to the e-mail client 18 a having sentthe e-mail message “E-mail Msg1” 72 at event 64, the application process58 a of the computing node N2 creates the corresponding locality controlobject (LCO_(Msg2)) 70, and replicates the data at event 68 to allreachable computing nodes (e.g., N1), and selectively passes thecorresponding locality control object (LCO_(Msg2)) 70 at event 68 to thecomputing node most appropriate to retain ownership of the e-mailmessage, namely the computing node N1 providing service for thedestination client 18 a.

Also note that the computing node N2 14 can continue to providedistributed client services 76′ even though the computing node wasdisconnected 78 from the rest of the resource group 16. In particular,assume that the e-mail client 18 bwas terminated prior to the e-mailclient 18 b receiving the e-mail message “E-mail Msg1” from thedistributed client service 76. Hence, the distributed client service 76continues to store the e-mail message for the terminated e-mail client18 b.

Assume now that the computing node “N2” is disconnected from theresource group 16 at event 78, for example due to the user of thecomputing node “N2” 14 moving the computing node from the network 10 toanother location (e.g., business travel). In this case, the applicationprocess 58 a of the distributed client services 76′ continues to providee-mail services to the e-mail client 18 b once the e-mail client 18 brestarts execution following the disconnection at event 78. Hence, theapplication process 58 a implements the distributed client service 76′by supplying e-mail messages (“E-mail Msg1”) to the e-mail client 18b(event 80), and “sending” e-mail messages having been sent from thee-mail client 18 b (event 82). The application process 58 a in thedistributed client service 76′ can choose whether to offer the e-mailclient 18 b based on whether the computing node N2 is in possession ofthe corresponding locality control object 70, and based on prescribedservice attributes 26; for example, the distributed client service 76′would provide read/write authorization for the received e-mail message“E-mail Msg1” based on determining that the e-mail client 18 b is therightful owner of the message, but provided read only authorization forthe e-mail message “E-mail Msg3” that was already transmitted by thee-mail client 18 b at event 82.

Hence, the computing node can resynchronize its service data 54 a′ withthe other computing nodes 14 of the resource group 16 upon reconnectionwith at least one of the computing nodes 14 belonging to that resourcegroup 16.

Hence, the distributed client service 76 can be provided by thecomputing nodes 14, even without all of the computing nodes 14 of agiven resource group being in communication at the same time; rather, asdescribed above, the distributed computing service 76 and 76′ isprovided based on each computing node 14 participating in thecorresponding resource group 16 according to the resource groupattributes 22. Data is resynchronized as each computing node 14 detectsreachability of another computing nodel4 a with in the same resourcegroup 16, and ownership of the data is determined based on identifyingthe computing node 14 that possesses the corresponding locality controlobject 70.

FIG. 5 is a diagram illustrating the method of providing distributedclient services, according to an embodiment of the present invention.The steps described herein can be implemented in each network node asexecutable code stored on a computer readable medium (e.g., floppy disk,hard disk, EEPROM, CD-ROM, etc.), or propagated via a computer readabletransmission medium (e.g., fiber optic cable, electrically-conductivetransmission line medium, wireless electromagnetic medium, etc.).

The method begins in step 100, where each computing node 14 reservesnode resources 52 for internal system use, including for example for useby the resource monitor 62, any client application 61 or 63, and thearbitration module 60. Alternately, the resource monitor 62 and thearbitration module 60 may be implemented as discrete components that aredistinct from the processor 44 and the memory 46. In addition, theresource monitor 62 determines the available node capacity and storesthe parameters in its entry table 32. It should be noted here in theresource monitor 62 continually monitors all consumption of resources inorder to determine if consumption of resources by an assigned consumer(e.g., a resource group 16) reaches a prescribed percentage threshold(e.g., 95%) relative to the amount of reserved capacity 34.

Assuming no new resource groups need to be created by the computing node14, the arbitration module 60 identifies in step 102 any availableresource groups (e.g., “S1”) 16, for example based on issuing a query tothe directory service 12 that requests identification of either allavailable resource groups 16, or selected resource groups havingselected service attributes 24 (e.g., e-mail application service) orselected data attributes 28. In response to receiving from the directoryservice 12 at least one resource requirement 24 for a correspondingresource group 16, the resource group arbitration module 60 determinesin step 104 whether the resource requirement 20 for joining theavailable resource group 16 is less than the available node capacity 32.If the resource requirement 20 is not less than the available nodecapacity 32 (i.e., the resource requirement 20 exceeds the availablenode capacity 32), the resource group arbitration module 60 decides tonot join the resource group, and determines whether to leave any joinedgroup to reclaim resources, described below.

If in step 104 the resource group arbitration module 60 determines thatthe resource requirement 20 does not exceed the available node capacity32, the resource group arbitration module 60 reserves capacity in step106 from the available node capacity 32, creates an additional entry 34for the reserved capacity, and joins the resource group 16.

The resource group arbitration module 60 finishes joining the resourcegroup 16 in step 108 by notifying the other computing nodes 14 alreadybelonging the resource group 16 of its having joined the resource group16. The other computing nodes already belonging to the resource group 16can then replicate their data associated with the resource group 16 tothe newly joined computing node 16 for storage in the associatedreserved data storage 54, enabling the computing resources 42 to executein step 108 the distributed computing services, for example byinstantiating the relevant software processes (e.g., 58 a).

It should be noted that each of the resource groups 16 are dynamic inthat their characteristics (identified by the stored attributes 22) maychange, in terms of resource requirements 20 due to additional loadingon the distributed services (e.g., due to more user nodes 18 requestingservice from the resource group 16) or an accumulation of stored data,or in terms of changes in the computing service attributes 24, forexample changes in service attributes 26 indicating that a new serviceis to be provided that differs from existing services, or that a similarservices to be provided using different resource types. Consequently,each of the resource group arbitration modules 60 are configured foradapting the resource groups 16 to changes in the computing serviceattributes 24, or the resource requirements 20, optimizing performanceof the resource group 16 and enabling the capacity of the network 10 toincrease based on creating new resource groups 16. Such changes,including splitting (i.e., dividing) and merging resource groups, aredescribed in the above-incorporated parent application entitled“DISTRIBUTED COMPUTING BASED ON MULTIPLE NODES WITH DETERMINED CAPACITYSELECTIVELY JOINING RESOURCE GROUPS HAVING RESOURCE REQUIREMENTS”(application Ser. No. 11/053,954, filed Feb. 10, 2005).

Examples of the distributed client services will now be provided. Assumein step 110 that the distributed client service 76 receives in step 110a request from the client 18 for data. As described above, an exemplaryclient is the e-mail client 61 (e.g., 18 a or 18 b), or the wordprocessing client 63. The application process 58 on the correspondingcomputing node 14 selectively provides in step 112 the requested data byproviding either read/write access to the requested data file (e.g., inthe case of a word processing client 63 having authorized access to datafor which the user has ownership), or read-only access (e.g., in thecase of an e-mail client attempting to read an e-mail message alreadyhaving been sent successfully to the distributed client services 76),based on the service attributes 26 indicating whether the client isauthorized to modify/write the data, or is restricted to read-only data.

In the case where the distributed client services 76 receives in step118 a request for storage of new client data (e.g., a new e-mail messageto be transmitted) the application process 58 in the computing node 14having received the client request stores the new client data as servicedata 54 a within the distributed file system of the distributed clientservice 76 based on creating a locality control object 70 for the newclient data, and a unique object identifier (OID) that uniquelyidentifies the new client data within the distributed file systemmaintained by the distributed client service 76 in the resource group16. Additional details related to creation of a unique object identifierfor storage of data in a distributed file system is described in theabove-incorporated application Ser. No. 11/051,333, entitled“ARRANGEMENT FOR A DISTRIBUTED FILE SYSTEM HAVING DATA OBJECTS MAPPEDINDEPENDENT OF ANY DATA OBJECT ATTRIBUTE”.

If in step 122 another computing node 14 is detected, the applicationprocess 58 replicates in step 124 the new client data and thecorresponding OID among the computing nodes 14 connected to the resourcegroup 16, and selectively transfers the locality control object 70 tothe most appropriate destination (see, e.g., events 66 and 68 of FIG.4). If no other computing node 14 is detected, the application process58 continues operations, and replicates in step 126 the data upondetecting reachability of another computing node 14 in the resourcegroup.

Hence, computing nodes 14 can provide distributed client services 76based on coordinating transactions between application processes 58 thatare executed independently on each computing node 14 according toprescribed service attributes 26, and based on managing and replicatingdata according to prescribed data attributes 28. In addition, datareplication and transfer of locality control objects can be passed todifferent computing nodes 14 as they are reachable; hence, computingnodes need not be simultaneously connected, but rather can be connectedand disconnected, each time synchronizing data and passing control usinglocality control objects.

As apparent from the foregoing, each of the application processes 58 ofthe resource group 16 have authority to perform read/write operations onthe distributed data, based either on possession of the correspondinglocality control object 70 or arbitration between the applicationprocesses 58 of the resource group 16 for transfer of the localitycontrol object, enabling any one of the application processes 58executed by any computing node 14 to provide the same read/write access.In addition, if the computing node is disconnected from the network andrequires the locality control object, instances may arise where thecomputing node may be able to create a new locality control object.Hence, the application process 58 executed locally on the same computingnode 14 as the executable client 18 will be able to provide read/writeaccess to distributed data, as needed. Once the computing node rejoinsthe network, the changes can be replicated to other members of thecomputing group. In addition, computing groups may be split or merged asnecessary, as described in detail in the above-incorporated application(application Ser. No. 11/053,954, filed Feb. 10, 2005), enabling theformation of personalized computing groups for personal services thatcan be merged with general computing groups once other users need accessto the personal services.

If in step 128 the resource group arbitration module 60 determines toleave a joined group 16, for example due to reduced activity in theresource group 16, or based on determining that the available nodecapacity has diminished below a prescribed threshold, the resource grouparbitration module 60 leaves the resource group 16 in step 130 bynotifying the other members of the resource group, and reclaiming thecapacity 34 that had been reserved for the resource group 16, andreturning the reclaimed capacity back to the available node capacity 32.Note that even though a computing node 14 implemented as a laptop coulddecide to leave a joined group in anticipation of being disconnectedfrom the network 10, the disclosed embodiment does not necessarilyrequire that the computing node 14 leaves the joined group 16 merelybecause it will be disconnected from the other computing nodes 14;rather, the computing node 14 still could continue to providedistributed services while disconnected from the other computing nodes14 of the resource group, and simply resynchronize data and stateinformation upon reconnection with the other computing nodes 14.

According to the disclosed embodiment, distributed client services in anetwork are provided by computing nodes having substantially differentnode capacities, based on each computing node selectively joining aresource group having a resource requirement that is less than theavailable node capacity. Each computing node that joins a resourcegroup, however, shares the same amount resources as specified by theresource requirement for the resource group, regardless of the overallcapacity of the computing node. Hence, substantially larger computingnodes can join a larger number of resource groups, providing distributedservice virtualization without concerns of loss of data if the largercomputing node becomes unavailable. In addition, substantially largercomputing nodes can be added to the network 10 without any adverseeffect on existing computing nodes 14 already in the network. Moreover,the replication of service data between the computing nodes of aresource group 16 according to prescribed data attributes 28, plus thecoordinated transactions between application processes according to theprescribed service attributes 26 in each of the computing nodes 14 thatbelong to the resource group 16, enable the computing nodes 14 toprovide a distributed client service that is still available even if oneof the computing nodes disconnects from the network.

While the disclosed embodiment has been described in connection withwhat is presently considered to be the most practical and preferredembodiment, it is to be understood that the invention is not limited tothe disclosed embodiments, but, on the contrary, is intended to covervarious modifications and equivalent arrangements included within thespirit and scope of the appended claims.

1. A method in a computing node, comprising: determining an availablenode capacity for the computing node relative to any resource groupshaving been joined by the computing node, each resource group having acorresponding resource group attribute specifying a resource requirementfor providing a corresponding distributed client service within anetwork, a service attribute that defines parameters for execution ofthe corresponding distributed client service, and a data attribute thatdefines service data to be used in providing the correspondingdistributed client service for a client; selectively joining at leastone of the resource groups based on the corresponding resourcerequirement being less than the available node capacity; and executingthe distributed client service for the corresponding at least oneresource group having been joined by the computing node, according tothe corresponding resource group attribute, including replicating thecorresponding service data among any other computing nodes belonging tothe corresponding at least one resource group according to thecorresponding service attribute and the corresponding data attribute. 2.The method of claim 1, wherein the executing includes receivingreplicated service data from one of the other computing nodes belongingto corresponding at least one resource group, the method furthercomprising: disconnecting from the network; and executing the client onthe computing node independent of the distributed client service andwhile the computing node is disconnected from the network, includingsending a request by the client to the distributed client service forclient data; the executing of the distributed client service includingsupplying the client data, from among the replicated service data, whilethe computing node is disconnected from the network.
 3. The method ofclaim 2, wherein: the executing of the client further includes sending asecond request to the distributed client service for transfer of secondclient data from the client to a destination; the executing of thedistributed client service further including identifying the secondclient data received from the client for replication in thecorresponding resource group based on the service attribute and the dataattribute, and replicating the second client data among the resourcegroup in response to detecting at least one of the other computing nodesbelonging to the corresponding resource group is reachable followingsaid disconnecting.
 4. The method of claim 3, wherein the identifyingincluding creating for the second client data a locality control objectthat defines ownership of the second client data, the distributed clientservice selectively providing the client one of read-only access orread/write access of the second client data following receipt of thesecond request by the distributed client service, based on the serviceattribute and the data attribute.
 5. The method of claim 4, wherein: thedistributed client service provides read-only access of the secondclient data based on the data attribute specifying the second clientdata is a message having been sent by the client for reception by adestination; the distributed client service provides read/write accessof the second client data based on the data attribute specifying thesecond client data is a data file that the client is authorized tomodify, the service attribute specifying the distributed client serviceproviding file system storage and retrieval for the client.
 6. Themethod of claim 2, wherein the supplying of the client data while thecomputing node is disconnected from the network includes selectivelyproviding read/write access to the client based on the service attributeand the data attribute.
 7. A method in a network, the method comprising:providing resource groups, each resource group having a correspondingresource group attribute specifying a resource requirement for providinga corresponding distributed client service within the network, a serviceattribute that defines parameters for execution of the correspondingdistributed client service, and a data attribute that defines servicedata to be used in providing the corresponding distributed clientservice for a client; in each computing node of the network: (1)determining a corresponding available node capacity relative to any ofsaid resource groups having been joined by the computing node, (2)selectively joining at least one of the resource groups based on thecorresponding resource requirement being less than the available nodecapacity, and (3) executing the distributed client service for thecorresponding at least one resource group having been joined by thecomputing node, according to the corresponding resource group attribute;and connecting a client, of the distributed client service, to thedistributed client service via one of the computing nodes having joinedthe corresponding resource group; wherein each of the computing nodeshaving joined said at least one resource group perform the executing ofthe distributed client service based on replicating the correspondingservice data among each of the other computing nodes belonging to thecorresponding at least one resource group, according to thecorresponding service attribute and the corresponding data attribute. 8.The method of claim 7, wherein the executing includes: receiving fromthe client a request by the one computing node for transfer of clientdata from the client; identifying the client data received from theclient for replication in the corresponding resource group based on theservice attribute and the data attribute; and replicating the clientdata among the resource group in response to detecting at least one ofthe other computing nodes belonging to the corresponding resource groupis reachable.
 9. The method of claim 8, wherein the identifying includescreating for the client data a locality control object that definesownership of the client data, the distributed client service selectivelyproviding the client one of read-only access or read/write access of theclient data following receipt of the request by the distributed clientservice, based on the service attribute and the data attribute.
 10. Themethod of claim 9, wherein: the distributed client service providesread/write access of the client data based on the data attributespecifying the client data is a data file that the client is authorizedto modify, the service attribute specifying the distributed clientservice providing file system storage and retrieval for the client; thedistributed client service provides read-only access of the client databased on the data attribute specifying the client data is a messagehaving been sent by the client for reception by a destination client,the distributed client service providing read/write access of the clientdata based on passing the corresponding locality control object to oneof the computing nodes belonging to the corresponding resource groupdeemed most appropriate to provide the distributed client service forthe destination client.
 11. The method of claim 10, further comprising:receiving from the destination client, by the one computing node deemedmost appropriate to provide the distributed client service, a requestfor the distributed client service; supplying, by the one computing nodedeemed most appropriate to provide the distributed client service, theclient data to the destination client, enabling the destination clientto obtain the read/write access of the client data.
 12. The method ofclaim 7, further comprising: detecting, by the computing nodes havingjoined said at least one resource group, a new computing node havingjoined the resource group; and synchronizing service data based on:replicating to the new computing node the service data based on one ofthe computing nodes having a locality control object for the servicedata, the locality control object defining ownership of the service datafor authority of read/write access of the service data; and replicatingfrom the new computing node new service data based on the new computingnode having the corresponding locality control object for the newservice data.
 13. A computing node comprising: a resource monitorconfigured for determining an available node capacity for the computingnode relative to any resource groups having been joined by the computingnode, each resource group having a corresponding resource groupattribute specifying a resource requirement for providing acorresponding distributed client service within a network, a serviceattribute that defines parameters for execution of the correspondingdistributed client service, and a data attribute that defines servicedata to be used in providing the corresponding distributed clientservice for a client; a resource group arbitration module configured forselectively joining at least one of the resource groups based on thecorresponding resource requirement being less than the available nodecapacity; and computing node resources configured for executing thedistributed client service for the corresponding at least one resourcegroup having been joined by the computing node, according to thecorresponding resource group attribute, including replicating thecorresponding service data among any other computing nodes belonging tothe corresponding at least one resource group according to thecorresponding service attribute and the corresponding data attribute.14. The computing node of claim 13, wherein the computing node resourcesare configured for receiving replicated service data from one of theother computing nodes belonging to corresponding at least one resourcegroup, the computing node resources further configured for: detectingthe computing node is disconnected from the network; and executing theclient independent of the distributed client service and while thecomputing node is disconnected from the network, including sending arequest by the client to the distributed client service for client data;the executing of the distributed client service including supplying theclient data, from among the replicated service data, while the computingnode is disconnected from the network.
 15. The computing node of claim14, wherein: the computing node resources further are configured forexecuting the client by sending a second request to the distributedclient service for transfer of second client data from the client to adestination; the computing node resources further are configured forexecuting the distributed client service by identifying the secondclient data received from the client for replication in thecorresponding resource group based on the service attribute and the dataattribute, and replicating the second client data among the resourcegroup in response to detecting at least one of the other computing nodesbelonging to the corresponding resource group is reachable followingsaid disconnecting.
 16. The computing node of claim 15, wherein thecomputing node resources further are configured for creating for thesecond client data a locality control object that defines ownership ofthe second client data, the distributed client service selectivelyproviding the client one of read-only access or read/write access of thesecond client data following receipt of the second request by thedistributed client service, based on the service attribute and the dataattribute.
 17. The computing node of claim 16, wherein: the distributedclient service provides read-only access of the second client data basedon the data attribute specifying the second client data is a messagehaving been sent by the client for reception by a destination; thedistributed client service provides read/write access of the secondclient data based on the data attribute specifying the second clientdata is a data file that the client is authorized to modify, the serviceattribute specifying the distributed client service providing filesystem storage and retrieval for the client.
 18. The computing node ofclaim 14, wherein the supplying of the client data while the computingnode is disconnected from the network includes selectively providingread/write access to the client based on the service attribute and thedata attribute.
 19. A network comprising: a plurality of computing nodesconfigured for selectively joining resource groups, each resource grouphaving a corresponding resource group attribute specifying a resourcerequirement for providing a corresponding distributed client servicewithin a network, a service attribute that defines parameters forexecution of the corresponding distributed client service, and a dataattribute that defines service data to be used in providing thecorresponding distributed client service for a client; each computingnode configured for: (1) determining a corresponding available nodecapacity relative to any of said resource groups having been joined bythe computing node, (2) selectively joining at least one of the resourcegroups based on the corresponding resource requirement of the secondresource group being less than the available node capacity, and (3)executing the distributed client service for the corresponding at leastone resource group having been joined by the computing node, accordingto the respective resource group attribute; wherein one of the computingnodes that executes distributed client service, in response to receivinga request from a client of the distributed client service, performs thedistributed client service for the client, each of the computing nodeshaving joined said at least one resource group perform the executing ofthe distributed client service based on replicating the correspondingservice data among each of the other computing nodes belonging to thecorresponding at least one resource group, according to thecorresponding service attribute and the corresponding data attribute.20. The network of claim 19, wherein the one computing node isconfigured for: receiving from the client a request for transfer ofclient data from the client, identifying the client data received fromthe client for replication in the corresponding resource group based onthe service attribute and the data attribute; and replicating the clientdata among the resource group in response to detecting at least one ofthe other computing nodes belonging to the corresponding resource groupis reachable.
 21. The network of claim 20, the one computing node isconfigured for identifying the client data based on creating for theclient data a locality control object that defines ownership of theclient data, the distributed client service selectively providing theclient one of read-only access or read/write access of the client datafollowing receipt of the request by the distributed client service,based on the service attribute and the data attribute.
 22. The networkof claim 21, wherein: the distributed client service provides read/writeaccess of the client data based on the data attribute specifying theclient data is a data file that the client is authorized to modify, theservice attribute specifying the distributed client service providingfile system storage and retrieval for the client; the distributed clientservice provides read-only access of the client data based on the dataattribute specifying the client data is a message having been sent bythe client for reception by a destination client, the distributed clientservice providing read/write access of the client data based on passingthe corresponding locality control object to one of the computing nodesbelonging to the corresponding resource group deemed most appropriate toprovide the distributed client service for the destination client. 23.The network of claim 22, wherein the one computing node deemed mostappropriate to provide the distributed client service is configured for:receiving from the destination client a request for the distributedclient service; supplying the client data and the corresponding localityobject to the destination client, enabling the destination client toobtain the read/write access of the client data.
 24. The network ofclaim 19, wherein the computing nodes having joined said at least oneresource group are configured for: detecting a new computing node havingjoined the resource group; and synchronizing service data based on: (1)replicating to the new computing node the service data based on one ofthe computing nodes having a locality control object for the servicedata, the locality control object defining ownership of the service datafor authority of read/write access of the service data; and (2)replicating from the new computing node new service data based on thenew computing node having the corresponding locality control object forthe new service data.
 25. A computing node comprising: means fordetermining an available node capacity for the computing node relativeto any resource groups having been joined by the computing node, eachresource group having a corresponding resource group attributespecifying a resource requirement for providing a correspondingdistributed client service within a network, a service attribute thatdefines parameters for execution of the corresponding distributed clientservice, and a data attribute that defines service data to be used inproviding the corresponding distributed client service for a client;means for selectively joining at least one of the resource groups basedon the corresponding resource requirement being less than the availablenode capacity; and means for executing the distributed client servicefor the corresponding at least one resource group having been joined bythe computing node, according to the corresponding resource groupattribute, including replicating the corresponding service data amongany other computing nodes belonging to the corresponding at least oneresource group according to the corresponding service attribute and thecorresponding data attribute.
 26. The computing node of claim 25,wherein the means for executing is configured for: receiving replicatedservice data from one of the other computing nodes belonging tocorresponding at least one resource group; determining that thecomputing node is disconnected from the network; executing the client onthe computing node independent of the distributed client service andwhile the computing node is disconnected from the network, the includingsending a request by the client to the distributed client service forclient data; executing the distributed client service based on supplyingthe client data, from among the replicated service data, while thecomputing node is disconnected from the network.
 27. The computing nodeof claim 26, wherein the means for executing is configured for:executing the client based on sending a second request to thedistributed client service for transfer of second client data from theclient to a destination; executing the distributed client service basedon identifying the second client data received from the client forreplication in the corresponding resource group based on the serviceattribute and the data attribute, and replicating the second client dataamong the resource group in response to detecting at least one of theother computing nodes belonging to the corresponding resource group isreachable following said disconnecting.
 28. The computing node of claim27, wherein the means for executing is configured for creating for thesecond client data a locality control object that defines ownership ofthe second client data, the distributed client service selectivelyproviding the client one of read-only access or read/write access of thesecond client data following receipt of the second request by thedistributed client service, based on the service attribute and the dataattribute.
 29. The computing node of claim 28, wherein: the distributedclient service provides read-only access of the second client data basedon the data attribute specifying the second client data is a messagehaving been sent by the client for reception by a destination; thedistributed client service provides read/write access of the secondclient data based on the data attribute specifying the second clientdata is a data file that the client is authorized to modify, the serviceattribute specifying the distributed client service providing filesystem storage and retrieval for the client.
 30. The computing node ofclaim 26, wherein the means for executing is configured for supplyingthe client data while the computing node is disconnected from thenetwork based on selectively providing read/write access to the clientbased on the service attribute and the data attribute.